Re: pg_hba.conf change in 7.4 - Mailing list pgsql-general

From Seum-Lim Gan
Subject Re: pg_hba.conf change in 7.4
Date
Msg-id p0510032abbf8fdb47e92@[192.168.10.94]
Whole thread Raw
In response to Re: pg_hba.conf change in 7.4  (Seum-Lim Gan <slgan@lucent.com>)
Responses Re: pg_hba.conf change in 7.4
List pgsql-general
Hi Bruce,

I tried to newly compiled 7.4 with HAVE_IPV6 commented out
in /src/include/pg_config.h.

After that I tried psql:

psql -U scncraft -h localhost
psql: FATAL:  no pg_hba.conf entry for host "::1", user "scncraft",
database "A"

This happens the same way whether I have this line in pg_hba.conf or not:
# IPv6-style local connections:
host    all         all         ::1
ffff:ffff:ffff:ffff:ffff:ffff:
ffff:ffff        ident pspmap

Thanks.

Gan

At 8:48 am -0600 2003/12/7, Seum-Lim Gan wrote:
>Hi Bruce,
>
>I am rebuilding now and noticed some error that I may have missed
>since the last time I build 7.4.
>Essentially the postmaster, bin, lib have been built and server is able to
>start and I am able to create a new DB and etc.
>Will let you know if the commenting out the HAVE_IPV6 will work.
>
>Meanwhile, the following probably needs to be looked at.
>Some background: src/template/solaris has been changed to use -mt instead
>of -pthread. Built with Sun Workshop in Solaris 9.
>
>"pl_funcs.c", line 403: warning: argument #1 is incompatible with prototype:
>         prototype: pointer to const unsigned char :
>"../../../../src/include/mb/
>pg_wchar.h", line 291
>         argument : pointer to char
>UX tsort: INFORM: cycle in data
>         pl_comp.o
>         pl_gram.o
>"plperl.c", line 317: undefined symbol: thr
>"plperl.c", line 317: left operand of "->" must be pointer to struct/union
>"plperl.c", line 323: left operand of "->" must be pointer to struct/union
>"plperl.c", line 323: left operand of "->" must be pointer to struct/union
>"plperl.c", line 323: left operand of "->" must be pointer to struct/union
>"plperl.c", line 323: left operand of "->" must be pointer to struct/union
>"plperl.c", line 437: undefined symbol: thr
>"plperl.c", line 437: left operand of "->" must be pointer to struct/union
>"plperl.c", line 443: left operand of "->" must be pointer to struct/union
>"plperl.c", line 443: left operand of "->" must be pointer to struct/union
>"plperl.c", line 443: left operand of "->" must be pointer to struct/union
>"plperl.c", line 443: left operand of "->" must be pointer to struct/union
>cc: acomp failed for plperl.c
>make[3]: *** [plperl.o] Error 2
>make[2]: *** [all] Error 2
>make[1]: *** [all] Error 2
>
>
>>Yes, you have to comment it out like the other items in the file.
>>
>>---------------------------------------------------------------------------
>>
>>Seum-Lim Gan wrote:
>>>  Hi Bruce,
>>>
>>>  Thanks for the recommendation.
>>>
>>>  I will edit the pg_config.h file and comment out the
>>>  HAVE_IPV6 #define.
>>>  It is now defined as 0.
>>>
>>>  Earlier on, I tried to set IPV6 to no or 0 in configure.ih
>>>  and then configure and rebuild but that did not work.
>>>
>>>  Will let you know if commenting out the HAVE_IPV6 will work.
>>>
>>>  Thanks.
>>>
>>>  Gan
>>>
>>>  At 11:28 am -0500 2003/12/6, Bruce Momjian wrote:
>>>  >Seum-Lim Gan wrote:
>>>  >>  Hi Bruce,
>>>  >>
>>>  >>  I wonder if there is any recommendation to this ?
>>>  >>  Is there a way to configure PostgreSQL to not use
>>>  >>  IPv6 ?
>>>  >
>>>  >One idea is to edit include/pg_config.h and comment out HAVE_IPV6 and
>>>  >recompile and see if it works.  That will disable the postmaster from
>>>  >listening on IPv6.
>>>  >
>>>  >--
>>>  >   Bruce Momjian                        |  http://candle.pha.pa.us
>>>  >   pgman@candle.pha.pa.us               |  (610) 359-1001
>>>  >   +  If your life is a hard drive,     |  13 Roberts Road
>>>  >   +  Christ can be your backup.        |  Newtown Square,
>>>Pennsylvania 19073
>>>  >
>>>  >---------------------------(end of broadcast)---------------------------
>>>  >TIP 3: if posting/reading through Usenet, please send an appropriate
>>>  >       subscribe-nomail command to majordomo@postgresql.org so that your
>>>  >       message can get through to the mailing list cleanly
>>>
>>>
>>>  --
>>>  +--------------------------------------------------------+
>>>  | Seum-Lim GAN                 email : slgan@lucent.com  |
>>>  | Lucent Technologies                                    |
>>>  | 2000 N. Naperville Road, 6B-403F  tel : (630)-713-6665 |
>>>  | Naperville, IL 60566, USA.        fax : (630)-713-7272 |
>>>  |       web : http://inuweb.ih.lucent.com/~slgan         |
>>>  +--------------------------------------------------------+
>>>
>>>  ---------------------------(end of broadcast)---------------------------
>>>  TIP 8: explain analyze is your friend
>>>
>>
>>--
>>   Bruce Momjian                        |  http://candle.pha.pa.us
>>   pgman@candle.pha.pa.us               |  (610) 359-1001
>>   +  If your life is a hard drive,     |  13 Roberts Road
>>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
>
>
>--
>+--------------------------------------------------------+
>| Seum-Lim GAN                 email : slgan@lucent.com  |
>| Lucent Technologies                                    |
>| 2000 N. Naperville Road, 6B-403F  tel : (630)-713-6665 |
>| Naperville, IL 60566, USA.        fax : (630)-713-7272 |
>|       web : http://inuweb.ih.lucent.com/~slgan         |
>+--------------------------------------------------------+
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faqs/FAQ.html


--
+--------------------------------------------------------+
| Seum-Lim GAN                 email : slgan@lucent.com  |
| Lucent Technologies                                    |
| 2000 N. Naperville Road, 6B-403F  tel : (630)-713-6665 |
| Naperville, IL 60566, USA.        fax : (630)-713-7272 |
|       web : http://inuweb.ih.lucent.com/~slgan         |
+--------------------------------------------------------+

pgsql-general by date:

Previous
From: "Claudio Lapidus"
Date:
Subject: Re: last update time of a table
Next
From: Michael Glaesemann
Date:
Subject: Re: user defined variable per session